From e134a69f5c649290accfe2d5e905c5810425b4c4 Mon Sep 17 00:00:00 2001 From: Jan Beulich Date: Tue, 3 Nov 2015 18:11:15 +0100 Subject: [PATCH] timer-op: demote a debugging message to really be debugging only The issue the message points out may have been of relevance during the early days, but shouldn't anymore. Signed-off-by: Jan Beulich Reviewed-by: Andrew Cooper Acked-by: Ian Campbell --- xen/common/schedule.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xen/common/schedule.c b/xen/common/schedule.c index c5f640fd73..292e9a07ed 100644 --- a/xen/common/schedule.c +++ b/xen/common/schedule.c @@ -1118,8 +1118,8 @@ long do_set_timer_op(s_time_t timeout) * timeout in this case can burn a lot of CPU. We therefore go for a * reasonable middleground of triggering a timer event in 100ms. */ - gprintk(XENLOG_INFO, "Warning: huge timeout set: %"PRIx64"\n", - (uint64_t)timeout); + gdprintk(XENLOG_INFO, "Warning: huge timeout set: %"PRIx64"\n", + timeout); set_timer(&v->singleshot_timer, NOW() + MILLISECS(100)); } else -- 2.30.2